Cream of the Crop 1

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 1 / Cream of the Crop 1.iso / BBS / ESC150.ARJ / ESC.DOC < prev next >

Wrap

Text File | 1992-08-02 | 64KB | 1,235 lines

Welcome to ESC version 1.5 8/1/92 EchoMail SetUp Configurator - EchoMail System Controller * 1.1 ESC IS DESIGNED TO DO THREE THINGS 1st: ESC facilitates and simplifies the installation process of a full FIDONET POINT or NODE compatible mailer. In testing, users have established a working mailer in less than ten minutes with little intervention from a second party. 3d and 4d systems are fully supported. 2nd: ESC manages an entire EchoMail system. As administrator, ESC coordinates the work, drawing upon existing software rather than inventing it again. ESC functions as an electronic-mail interface where all functions are controlled from menus rather than user created batch file processing. ESC creates the batch, control and menu files and the user orchestrates them from a convenient menu system. 3rd: ESC provides a living example of a working electronic mailer system. In other words, consider it an instructional frame work where a user can observe a free form, basic and streamlined setup. With a little scrutiny and tinkering a user can understand the obscure structure of an email system, giving the environment to experiment in and one day have exactly what they want rather than a setup which comes in a can. * 1.2 CONTENTS ESC design and purpose . . . . . . . . 1.1 Table of Contents . . . . . . . . 1.2 What's needed . . . . . . . . 1.3 Installing ESC . . . . . . . . 1.4 Primary Operation . . . . . . . . 1.5 General Overview . . . . . . . . 1.6 System and Software . . . . . . . . 1.7 a. Executables . . . . . . . . b. Fossils . . . . . . . . c. Utilities . . . . . . . . OS/2 support . . . . . . . . 1.8 WIMM personal msg search . . . . . . . . 1.9 YABOM - O/B manager + Polling with the timer . . . . . . . . 2.0 Detailed Installation . . . . . . . . 2.1 a. 4d Points . . . . . . . . Detailed Operation . . . . . . . . 2.2 a. Menu Options . . . . . . . . 1. Adding new areas . . . . . . . . 2. Setting msg limits . . . . . . . . 3. Removing old areas . . . . . . . . Bonk & the ESC nodelist . . . . . . . . 2.3 Msged or Golded . . . . . . . . 2.4 Changing addresses . . . . . . . . 2.5 Nodelist Processors . . . . . . . . 2.6 Node Operation . . . . . . . . 2.7 Hosting 4d points Domain Support Caveats . . . . . . . . 3.1 Problems . . . . . . . . 3.2 3d/4d . . . . . . . . Acknowledgements . . . . . . . . 4.1 Disclaimer . . . . . . . . 4.2 Bugs and Problems . . . . . . . . 4.3 Upgrading . . . . . . . . 4.4 Customizing . . . . . . . . 4.5 Glossary . . . . . . . . 5.1 * 1.3 OTHER PROGRAMS NEEDED FOR THIS ECHOMAIL SETUP In its simplest form, here is what's needed: BT.EXE (EMSI) version 2.56 front end mailer MSGED.EXE version 2.1 message reader SQUISH.EXE version 1.01 mail packer BNU.EXE version 1.7 fossil (or X00 or Opuscom) All are available from most FIDONET systems. * 1.4 INSTALLING AN ECHOMAIL SYSTEM USING ESC (1) From the ROOT directory of your hard drive, type md \bt (2) Copy ESC and the files listed above into this directory. (3) You will need to know, and perhaps experiment with your modem's initialization string. You'll need information from the HOST, who will supply your echomail. Having this person on the phone or present at installation is ideal. (4) Run ESC.EXE, answering the questions with information from the above source, and filling in your preferences. ┌───────────────────── !! VERY IMPORTANT !! ─────────────────────┐ │ Answer each question in the same format as shown in each │ │ example!. If you become creative or unreasonable, the data │ │ written out will not make sense and your mailer will not work! │ └────────────────── !! FOLLOW THE EXAMPLES !! ───────────────────┘ The Installation is complete. These are the essentials. What's left is the fine tuning. The remainder of this document will try to supply answers, warnings, and general information. * 1.5 Operating ESC as an Echomail system If you chose the default directories which ESC offered, the next two steps should have your system in operation. (1) cd \bt ... at the prompt: MAIL <ENTER> (2) Choose from the menu: ESC - to edit parameters CALL - dial BOSSNODE (HOST system) UNATTND - dial any system listed in your nodelist DELAYED - poll scheduler PACK - prepare OUT mail for sending TOSS - prepare IN mail for reading EDITOR - read mail / write messages (Msged or Golded) AREAS - to add new mail areas SQUISH - maintenance (submenu) for message areas HELP - list feature information QUIT - does just what it says This is only a portion of your options. Should you choose the SQUISH feature, you'll be moved to the next of two more submenus which contain all the functions this setup offers to maintain your message areas (from a menu). The next menu down offers nodelist, outbound and message search utilities. Each menu is accessed by referring to it by number or letter options. * 1.6 GENERAL OVERVIEW OF ESC ESC is capable of more than what this intentionally brief document reveals. As you work with the files which ESC has created and the other software and documentation that are a part of your total system, you will find ESC to be a complete application program. ESC consolidates and manages all the features and functions needed to support a FIDONET compatible POINT mailer. Even a NODE system can be operated under ESC with primary level support. A traditional mailer is more than one program. Due to the talents and generosity of certain programmers, much of the operation has already been consolidated. Squish is a good example. Scott Dudley has incorporated many functions of mail handling into one neat package. Still, the example configuration files contain more than is needed by the first time user. So those configs initially look intimidating. This is where ESC shines. It creates basic config files which will serve the purpose for a first-time-up system. ESC also can keep any features which you later add to those very same configs. Those simple configs can be built into more complex ones as the user is capable of understanding them. The idea behind ESC is to initially install and operate an echomail setup while allowing a configurable system environment. ESC utilizes the popular freeware packages available throughout the FIDONET community. The required executables are found listed in this document. Included are the terminal interface, message creator / reader, complete mail processor and an assortment of utilities. ESC orchestrates all of these from a menu driven interface. Which, you may have noticed, is the secondary function of ESC. The primary function is to create all the configuration and batch files associated with the software. All this work is accomplished in less than a minute, once you've answered the questions. NOTE: ESC will also create a miniature NODELIST on request. By nature, electronic mail networking is difficult to comprehend and uses a lot of abstract terminology, most of which is beyond the scope of this and any one single document. Keep in mind that FIDONET has been built with a hobbyist mentality. Therefore, the best source of information is the group of people who are already involved. ESC attempts to ease the difficulty of getting started by safely putting the novice into active participation right away. * 1.7 SYSTEM AND SOFTWARE REQUIREMENTS As of this version, 350 to 400k of RAM is recommended. ESC was developed on an AMI 386sx bios system, under DOS 5.0, in a 400k DESQview window under QEMM 6.0. It has been tested on several machines ranging from a 4.77 mhz XT monographic setup under DOS 3.3 to a full featured 33mhz 486DX. For practical purposes you should have several megabytes of free disk space. This would indicate that you really should be running your mailer from a fixed disk. Still, it is possible to operate from a high density (or two) floppy drive system. SOFTWARE INCLUDED: The distribution archive should contain a minimum of the files listed below: ESC.EXE ESCUTIL.EXE DOTHIS.COM ESC.DOC ESC_HELP.DOC All the executables are necessary to set up and maintain your integrated mail system interface. SOFTWARE YOU WILL NEED: In addition to the above files, you will need those listed below to operate your FTS mailer using ESC. Any good FIDONET system (there are over 15,000 of them in 42 or more countries) should have them all. USING ESC IN ITS SIMPLEST FORM: For example, if you have a mono single tasking system with Ansi.Sys included in your Config.Sys, and you will be a POINT to a system which uses session level passwording, all you will need are the following: BT.EXE version 2.50 front end mailer MSGED.EXE version 2.0.5 message reader SQUISH.EXE version 1.00 mail packer BNU.EXE version 1.7 fossil LIST.COM any version dir/file multi-utility PKZIP.EXE version 1.10 file archiver PKUNZIP.EXE version 1.10 file archive extractor Or, you can build a larger, more complex system. ESC may access any of the programs listed below, in addition to the ones above depending on your configuration. One of these fossil drivers X00.EXE version 1.24 BNU.EXE version 1.7 OPUSCOMM version 5.3 (with) OCOM_CFG Only if you'll be using a NODELIST QNODE.EXE version 1.42 NODELIST compiler QIDX.EXE comes with Qnode XLAXNODE.EXE version 2.53 NODELIST compiler BONK.EXE version 1.74 (v7 NODELIST) & outbnd util YABOM.EXE version 1.10b (v7 NODELIST) & outbnd util If you're not loading ANSI.SYS on boot up ANSI.COM version 1.3* If you're running a color system VFOS_IBM.COM version 1.10 VFOS_DEL.COM version 1.00 If you want your mail areas searched for personal messages. WIMM.EXE version 1.0 Message search utility * = Ziff Communications / PC Magazine A complete compliment of file compression programs is recommended. Such as Phil Katz PK - everything. Haruyasu Yoshizaki LHA - LHARC. NoGate's PAK, Rahul Dhesi's ZOO program and Robert Jung's ARJ... The compression programs: ARCA - Wayne Chin and Vernon Buerg ARCE - Vernon Buerg are the defacto standard recognized throughout fidonet for mail compression. All systems should be capable of handling another's mail in this form. However, most systems can process other forms of compressed FTS mail (bundles) as well. Esc defaults to using PKZIP by Phil Katz because of its availability and efficiency. You can specify something else after your setup is complete, from the ESC editor mode. Check with your BOSS (or HOST) system before changing it. * 1.8 OS/2 SUPPORT ESC is not an OS/2 program. If it is run under OS/2, it must be executed in a DOS box. All the necessary verbiage is within the ESC source for OS/2 support. The only thing lacking is for ESC and the support files to be ported over. * 1.9 WIMM SUPPORT ESC builds a WIMM.CFG whenever it creates the message editor configs. WIMM is written by Gerard van Essen. It searches your Squish.Cfg file, then scans each message area listed for your name. If a message is found, it will be copied into the PERSONAL message area which Esc creates for you. This way, you will be unlikely to miss any messages sent to you via the echoes. YABOM SUPPORT YABOM - Yet Another Binkley Outbound Manager is a multipurpose utility which is of particular interest to NODE systems. POINT mailers can benefit from its many features as well. YABOM will not appear on the (3rd) menu until YABOM.EXE exists in the same directory as the MAIL.BAT. You should have all the associated files for YABOM there as well. If you haven't configured YABOM before calling it from the MAIL menu, you'll be given the choice to do so at that time. You will need to know more than a little about your directories and addressing when you configure YABOM. * 2.0 Polling with the TIMER You can set up to 20 automatic poll times using the [D]elay Poll option from the 1st (of 3) MAIL menus. Not much has to be explained as the function is fairly self explanatory. One thing to remember is polling times must be set using a 24 hour method and the format entered must be HH:MM exactly. If you want your system to poll the host at 10:30 in the evening, you must specify 22:30. Polling isn't all the Timer will allow you to do. By editing the ESCTIMER.BAT, you can specify anything you wish. * 2.1 Detailed INSTALLATION ESC's purpose is to make installation and operation as simple as possible. The first step is to create a directory for ESC and the other files that are needed. You can name the directory whatever you want, however the recommendation (default) is \BT. All your operations should now be handled from this directory. Simply move into this home directory and control everything concerning your mail system from it. ESC and all the files it creates need to reside in this home directory. For now, it is essential to have ESC.EXE in there. If you choose to have ESC create the tiny NODELIST, and you'll need one in most cases, be sure to have the QNODE (with QIDX) or XLAXNODE executable accessible through the DOS path. Now, type in ESC and follow the instructions as they appear on your screen. Please pay attention to the bottom Information: window. The best way to initially install and operate your mailer is to be in contact with your mail source (HOST) at the time of serious configuration. Most terms used in the Fido network are ambiguous to the uninitiated. Your BOSSNODE (HOST) sysOp will know what all of them mean. The glossary at the end of this document may be of help as well. BOSSNODE and HOST from your standpoint are terms associated with the system/operator which will be the resource from where echomail destined for your system is obtained. In other words, your HOST is the next step up in the network. You'll receive and send mail from and to this system. The operator of this system must supply you with particular information in order for your mail transactions to be successful. It would be helpful if this sysOp has at least some working knowledge of this software package. The ideal situation is to sit in front of the computer, phone perched on your shoulder, while your HOST answers your questions. There are a number of things you must find out from this person anyway. You will need to enter your assigned POINT or NODE address, phone number, etc. You'll also need to know a working initialization string for your modem. Without it, you'll be all dressed up with no place to go. A word of warning: modem inits can be a bear! Just remember that BINKLEY uses the | (pipe) in lieu of the common ^M as an initialization string carriage return. NOW, run ESC.EXE and answer all the questions carefully, reading the information window completely as you progress through the questions. If you do make an entry mistake, you will be given the opportunity to make corrections at the end of the questionnaire. This can be taken care of from the CHANGE menu item.. Don't hurry! COMMAND LINE SYNTAX: ESC EXAMPLE: C:\>ESC ESC runs in two modes: CONFIGURATION and EDIT. EDIT mode isn't available until your setup has been configured. In other words, CONFIGURATION mode is the only mode you will have until ESC has done its initial setup work and has written the configuration and batch files. ESC will prompt you for information which allows the program to write the configuration files for BINKLEY, QNODE, XLAXNODE, BONK, SQUISH, MSGED, GOLDED and WIMM. ESC will optionally provide a "bare bones" NODELIST (NODELIST.001). You can forego ANSI.COM if you already have a comparable device handler loaded at runtime of the batch file named MAIL (Your ESC menu operation master batch file). Another batch file (MAKEDIR) is also created to quickly create the subdirectories needed for your mailer and editor to work. Why does ESC create batch files to control the mailer? DOS batch files have two advantages. The main one being, batch files can be edited easily to suit custom applications. You will be able to change things to suit your particular preferences simply by editing these files should the desire strike you. Secondly, the processing of a batch file requires only 96 bytes of RAM. MS-Dos batch processing speed (the lack of it) is the disadvantage. When ESC.EXE is initially run, (CONFIGURATION MODE), its job is to create control files. Here is the list. All of them are applicable except perhaps the AREAS.BBS. However, it has such widespread use that it is considered a standard application file. Therefore, ESC provides a very basic one. At the present time ESC doesn't update or maintain it as it does the other control files because currently there is no need. Files Created by ESC AREAS.BBS - Universal message area control (unused) BINKLEY.CFG - BinkleyTerm control file BINKLEY.EVT - BinkleyTerm event control file BINKLEY.LNG - BinkleyTerm information file BONK.CFG - nodelist utility configuration file COMPRESS.CFG - Squish archiving information control ESC.CFG - ESC configuration information MAIL.BAT - ESC menu interface batch file MAKEDIR.BAT - ESC subdirectory creation file DOMSGED.BAT - MSGED editor process batch file GOTMAIL.BAT - AFTERMAIL Binkley mail processing MSGED.CFG - MSGED information control file GOLDED.CFG - GOLDED information control file NODELIST.001 - Node address lookup (optional) QNODE.CFG - Nodelist compilation control file XLAXNODE.CTL - Nodelist compilation control file POLL.BAT - Simple automatic Polling batch file ROUTE.CFG - Squish routing information control SQUISH.CFG - Squish mail handling control file WIMM.CFG - Personal mail search control file MSGEDIT.BAT - Binkley Alt-E editor call up batch ESCTIMER.BAT - Delayed Polling batch file OKFILE.LST - Sample f/req ok list for node operation + M_AREA.DAT - Msged message area definition (upgrade) + S_AREA.DAT - Squish message area definition (upgrade) * MAIL.BAT serves as a menu to the other files and functions. * POLL.BAT serves to fully automate the POLLing process. + Only created if upgrading and requesting to save the old message area configuration. After ESC has created all your configuration files, it will then function as an EDITOR to them. ESC also can recreate your setup from scratch if you so desire. A few precautions need to be made clear at this time. ESC preserves edits made outside of its own editor on several files such as the Binkley, Squish and Msged configurations files. It also will create a .BAK if instructed to overwrite, on nearly all files. However, keep in mind that if you make an alteration to the MAIL.BAT, for instance, and then have ESC write a new one, your edits will not be included. They will now exist in the MAIL.BAK. If you write the file out twice, the edits will be moved into the bit bucket and are gone for good. A warning is issued before you can globally rewrite your entire configuration. You should gain an understanding of your configs as soon as possible. Don't be intimidated by the terminology. Simply follow each step. The process will take less that ten minutes. Keep in mind that parameters can be readjusted later. When you have finished all your entries, tag all configurables from the menu presented. On a scratch creation all files are automatically tagged. Either press F or page down to * FINISHED * and hit ENTER. ESC will notify you that it is writing the necessary configurables, batch and support files. You will hear a chirp if any of the files already exist; this is telling you that ESC is backing them up before overwriting them. You may press any key to exit this portion of ESC when the process has finished. ALL the files referred to in this document are available in complete archive format from 1:157/534 You may request the list in order to obtain the proper names as "ESCLIST.LST". Complete information concerning file names, dates and sizes are within this text file. You might want to request FILES to see exactly what is available from this system. FOR 4d POINT CONFIGURATION Creating a 4d setup is straight forward. Respond appropriately when prompted whether this is to be a node or POINT setup and then whether it is to be for a 3d or 4D configuration. You should be certain which type of addressing your HOST supports. * 2.2 OPERATING THE ECHO MAIL SYSTEM After you have answered all the questions from the configuration mode and have written out all the files, you're ready to make your first call to the HOST system. ESC has created two methods of doing this. The first and easiest is to type POLL at your DOS prompt while in your mailer's directory. The second is to type MAIL in the same fashion. Here is a brief explanation of both methods: MAIL.BAT is a somewhat autonomous function menu which gives the user the most control over what the mail system is doing. Using this menu requires some understanding of terms like TOSSing and PACKing of mail. There is a help screen provided from the MAIL menu. Also, the ESC_HELP.DOC has a step by step procedure for primary operation. An alternative to the MAIL menu is another batch file which substitutes control for simplicity. This batch file is named POLL.BAT. POLL.BAT controls your message handling, polling and message editor completely. Using it requires a minimal level of understanding. You'll eventually find yourself using the MAIL menu as opposed to the POLL method. When you do come to this point, you'll be faced with a list of options. Most of them are self explanatory. Below is a list which will give you a preview. For further help, check the definitions in the GLOSSARY at the end of this document. ESC accesses MSGED, the Squish-compatible version developed by John Dennis, or Golded created by Odinn Sorensen. The original MSGED format was created by Jim Nutt and released into the public domain. As of the 2.0.5 version, two help menus are accessible, if you have the two files associated with the help function. These being EHELP.HLP and RHELP.HLP. Pressing Alt H in either EDIT or READER mode will bring up the appropriate help screen. Just make certain that these files are in the same directory with MSGED.EXE. While on this subject, I've taken the liberty to reassign a few keys in a way that I feel is beneficial for someone unaccustomed to MSGED. First of all, I changed the ESCAPE key to move you out of the current message area and into the AREA selection list. This replaces the default of exiting MSGED, something which plagued me until I changed it. Also, you may view the list of message headers in an area simply by pressing the L key while in the reader mode. You can use the FIND function by just pressing the letter F as well as Alt-F. Finally, I reassigned the comma and period to be read-thread direction keys. Golded is fairly straight forward in its installation. The appropriate files are included in its own archive. These files should be located in the same directory as Esc. Esc will create a very basic but functional configuration file for use with Golded. Because Golded must use its own nodelist, you will need to create that and place it in the directory with Golded. One of the advantages of using Golded is the direct support for spell checking. Take a look at the Golded.Cfg which ESC creates and you will see a line commented out which makes reference to SS.EXE. Read the documentation for Golded and determine how you need to edit the Golded.Cfg to implement a spell checker. ESC will honor your change and keep your modification on subsequent re-writes of the Golded.Cfg. When you select either of these editors during setup or later in an editing session, the batch files will be written to access your choice. MAIL MENU CHOICES EXPLAINED - ESC - This brings up ESC in edit mode. Here, you may change quite a few parameters concerning your mailer in three modes: (1) Your SYSTEM configuration, (2) the BOSSNODE specifications, and (3) NODELIST items. The editor is a quick method for changing things like your fossil, system name, BOSSNODE, phone numbers, etc. The list is fairly extensive. This provides an alternative to re-configuring from scratch. Remember, you must WRITE the new files once you've re-configured them! Some changes require you to recompile your NODELIST if you are using one. - CALL - or - POLL - If your modem is connected, and you have configured your setup correctly, your system will dial out to the HOST system which you have previously established to be your echomail resource. If you have mail waiting, it should be delivered. If you have mail to be sent out, it should be sent. - UNATTND - Bring Binkley up in a waiting mode. Here it will sit and attempt to send any pending outbound mail on intervals. It will also "watch" the keyboard for your commands. Press ALT-F10 for a display of what Binkley can do, you'll be impressed! - DELAYED - This is the EscTimer mentioned previously. You are prompted to enter as many as 20 specific times in which your system will begin polling your Host system. This works well for someone who wants to pick up (or send) mail at a time when they are asleep, away or just in the mood to have their mailer do something all by itself. This is no match for Binkley's event schedule but it is a quick and easy way to accomplish scheduled polling. - PACK - Is the process which must be done after you create a message. This is a bundling process which prepares and addresses your message(s) to be sent out of your system via the modem. Normally this is done immediately after you create mail. The setup asks you if you wish to process (PACK) your new mail immediately after exiting your editor. For one reason or another you may wish to say no. You can then choose the PACK feature from the main menu and process your outbound mail at that time. - TOSS - Is the process which must be done after you RECEIVE messages. This is the unpacking of the mail bundle which has arrived on your system. This mail needs to be placed (TOSSed) into the individual mail AREAs before you can read it. - EDITOR - This is referred to as your message reader, although it also creates, quotes and edits messages. You need to KNOW these few key presses, otherwise you may get stuck in the reader: ALT X gets you out. The ESCAPE key offers you options. ALT E allows you to create new messages. ALT Q allows you to quote and reply to an already existing one. ALT S or the F1 key will save your new message. ALT C gives you the opportunity to change a message that has already been saved. ALT A allows you to select a new mail area. ALT L, or just the L key lists the messages that are contained in the area. ALT O shells you out of the editor, and typing EXIT will bring you back in. - AREAS - Is a special feature which should be used only after you have learned how to request new echomail areas and have received mail from them into your system. AREAS updates your config files to KNOW that you have new mail areas. Once run, and the new areas have been created, the messages which have been received and are waiting in the BAD MESSAGE area should be automatically TOSSed into the newly configured areas. - SQUISH - Is the mail handling submenu which includes the many functions provided by its author. This submenu can access five SQUISH type message base utilities associated with the SQUISH mailer: SQPACK - message maintenance (clean up) utility. SQINFO - message information utility. SQFIX - message area repair utility. SQREIDX - message area index repair utility. SQSET - individual message area size/date maintenance. SQSET is added only as a convenience. SQSet is a "manual" squish area maintenance utility. However, ESC supports its usage in a rather limited fashion. If you wish, you can edit the batch files which ESC creates to perform customized maintenance from the menu system provided. For practical purposes you may not need to bother with SQSet. Read the documentation which comes with the Squish mail processor for more details about using SQSet, your messages areas and the care and feeding of them. Additionally, there are a few more options from this menu. One of these being XAREAS which allows you to remove echomail areas from your configs, and another option named DIRWORK which access Vernon Buerg's LIST program and places you in your MSG directory. There you may view and perform DOS directory operations on the files. Such as to delete defunct areas. You can also purge (SQPack) your BAD MESSAGE area to free up space on your drive. However this should have been done automatically after you use AREAS from the main menu. Finally an option exists to globally delete the backup message files which SQFix creates while repairing damaged message files. These can be seen to have an extension which has a format something like <filename>.XX?. In most cases these files are useless and need to be deleted. - HELP - Menu features defined. - QUIT - Speaks for itself. (a) ADDING MESSAGE AREAS to your SQUISH.CFG and MSGED.CFG There are TWO ways: 1. Choose the AREAMAN option from the SQUISH submenu, which is chosen from the MAIL menu. Follow the prompts, you then can request the specified echo(es) from your echomail feed. 2. Request new echoes from your HOST. After they arrive, they will be TOSSed into your BAD MESSAGE area. Take a look to be sure they are there. From the ESC MAIL Menu: Choose [A] - AREAS add new areas. If all went well, you should see that the new areas have been created and the messages which were in your BAD MESSAGE area have been TOSSed into the newly created ones. (b) SETTING AREA MESSAGE LIMITS There is an option from the 2nd menu presented when you type MAIL at your Dos prompt. The SETSIZE option allows you to define exactly how many messages are allowed for an individual area. Initially, ESC offers a global static value which limits all areas to 200 messages. However, you may alter individual limits after ESC has created its MAIL menu system. To explain a little more in detail, some areas do not need to take up much room on your drive because of light traffic through them. Therefore allowing a limit of 200 messages in those areas would be a waste of space. On the other hand, some echoes may require a high limit due to the amount of messages which can be received in a short period of time. Because you don't want your oldest messages to be dropped off the end before you have had a chance to read them, you may wish to set a high message limit for such an area. With SETSIZE you simply choose the option and follow the prompts. (c) REMOVING MESSAGES AREAS from MAIL.BAT, SQUISH,and MSGED.CFG. When you no longer receive messages into a particular echomail area you need to tell your system that this is the case. There is a feature of the SQUISH submenu, accessed from the MAIL menu, called XAREAS. This option removes the area names from your control files so they won't be processed any longer. Here's how to operate this function. XAREAS will display your message areas and number them. You can then tell XAREAS which message areas you wish to delete from your control files. You should then go into the MSG directory and delete the mail files associated with the areas which you have removed in order to free the space they are taking. You can use DIRWORK to do this if you have LIST on your system. * 2.3 BONK AND THE ESC NODELIST Don't be intimidated by this next paragraph. The nodelist which ESC creates will function adequately with your bossnode. However some folks may wish to alter it to add in other systems. This is primarily who the following paragraph is addressed to. Bonk is a nodelist (fidonet system address lookup list) utility created by Tom Kashuba. As a dual faceted program, it allows you to somewhat visually manipulate the contents of your outbound directory as well as permit you to view and make changes to your nodelist. Bonk version 1.74 is restricted to accessing a version 7 nodelist. This is what ESC creates. Bonk does not only read the little nodelist which ESC creates but it can alter, add to and/or amend it. Bonk will also allow you to manipulate pending outbound mail files in your outbound mail area. You should read the BONK documentation to get a better idea of what it is. If you have BONK on your system, it can be accessed via the last (3rd) ESC menu. You may prefer to edit your little nodelist simply with a good text editor. With a little understanding of the structure of a nodelist, you will be able to edit it to suit your needs. Be certain to retain the control Z at the end of NODELIST.001! Also be sure to compile it afterwards using Qnode or another version 7 nodelist processor. * 2.4 MSGED OR GOLDED Both the ESC setup and editor support configurations for the Golded and Msged message reader/editors. Of course you must have either or both of these programs and any supporting files available to your system in order to appropriate their use. If possible, run Golded from the same directory that Esc is in. This solves numerous problems. * 2.5 CHANGING ADDRESSES The ESC editor permits you to change your address type... By choosing option F) Mailer type, you can switch from a 3d point to a 4d point and back. You can also switch points of either type to a node. You can change from a <HOST> system to a non host. You can even change from a node back to either type of point. ALWAYS write out the pertinent files associated with the change. Changing mailer types will cause ESC to want to recompile its nodelist. You may handle that in regard to your situation. If you do not want to write out all your configuration and batch files, there is a text file included in the archive called ESCFILES.TXT which gives a graph of which files are affected by changes by the ESC editor. Although changing mailer types does work from the editor, you might consider a new installation in a clean directory. This way you can be certain that nothing telltale will be left behind. One situation is the ROUTE.CFG for Squish. ESC parses and alters only that which it thinks is appropriate for the mailer type being setup. Changing from a NODE to a POINT system will remove the SEND verb from the ROUTE.CFG. Changing back to a NODE from a POINT cannot re-insert it. In other words, mail will not be sent directly to a point off of a node system which has been altered this way. This is more a matter of logic than of limitation. * 2.6 NODELIST PROCESSORS As mentioned before, ESC will create its own mini nodelist on demand. This still has to be compiled for use with Binkleyterm, Bonk, Yabom and Msged. If you chose to allow ESC to create the nodelist, you will be asked if you want to compile it. If you answer yes, you will then be given a choice of which compiler to use. You must have available, the one chosen. The choices are, Qnode (freeware by Jim West) and Xlaxnode (shareware by Scott Samet). Both work perfectly, however using Xlaxnode will warn you that there is a CRC error at runtime, you can ignore this warning. Your Nodelist will still work just fine. Note: Qnode must be accompanied with QIDX.EXE in order to index (and create) the nodex.idx and sysop.idx. QIDX.EXE is a part of the entire Qnode package. Both Qnode and Xlaxnode also create the FidoUser.Lst which is called upon by Golded and Msged. * 2.7 NODE OPERATION A living NODE system is just as easily setup and maintained as a point mailer. The major difference is the potential of a Node operation is further expanded. HOSTING 4d POINTS Either 3d or 4d Points are supported from the Node operation. 3d is more straight forward but 4d works perfectly well. It has been tested here and is running fine. A word of advice is in order. Please read the BINKLEY 2.40 document release on 4d point directory and domain support. This document may be a little difficult to find but it tells everything you need to know about the subject. DOMAIN SUPPORT Domain is almost entirely supported from the setup module. However, the Domain line in the Binkley.Cfg which ESC writes, is commented out and left for you to edit according to your own situation. Under the default circumstances a POINT mailer which has a domain designated in its address will properly pass mail to and from its host system. However, you will have to work with your configuration when attempting to pass mail to other systems, IF you designate a domain on your address. You must tell ESC that you want your mail to be ROUTED DIRECT in the System Option menu and have ESC (re)write your ROUTE.CFG.. * 3.1 CAVEATS If you should choose to alter any batch or configuration files which ESC generates, beware that changing your configuration and then having ESC rewrite files from the edit mode may overwrite your changes. ESC is semi-smart in that it scans several files and changes only the pertinent information leaving a .BAK file of the original and your edits in the new one. However, count on nothing. Simply backing up or copying the files involved to a safe place is good insurance against disappointments. A warning and brief explanation appear before you are in the position to possibly lose custom edits. If you let ESC do all your editing, you have nothing to worry about even if you tag all files to be overwritten. It is only when you change your files with a text editor that you "may" be in danger of losing those changes. An explanation of the workings of ESC when parsing and editing control files would extend this document beyond reasonable length. Therefore, tagging files to be rewritten is something you should investigate when you get to the point where you begin customizing your setup beyond the scope of ESC's simple echomailer concept. On the other hand, ESC makes such an attempt at keeping certain information intact that NEW versions of ESC will have features that cannot be accessed until the old file(s) have been removed. For instance, let us assume that a later version of ESC includes a new verb in the Msged.Cfg. Simply running the new version of ESC and telling it to write out a new Msged.Cfg will not place the addition into the old Msged.Cfg. The reason is that as long as ESC detects a Msged.Cfg it will not overwrite it. It will merely copy the file to a .BAK then create a new one by editing the one which exists. This procedure is consistent with several other files also. All that is being said here is this: ALLOW ESC TO DELETE THE OLD CONFIG(S), THEN TELL ESC TO WRITE THEM AGAIN WHEN UPGRADING TO A NEWER VERSION OF ESC! Doing this forces ESC to place newly added features into the file(s). The draw back is that you will lose any edits you have added previously. You will then have to re-enter those edits with a text editor. EDITING : The files which ESC writes are pretty much bare bones examples. BinkleyTerm's "BINKLEY.CFG" is one instance of a file which really can be expanded upon. Some optional items have been included and commented out in the .CFG to help in the case of problems initializing the modem. There are a number of others. Also, the BINKLEY.EVT is stark but is there to give you a base to work with and to allow Binkley to function in the Unattended mode (NODE installation). The POINT setup doesn't require the BINKLEY.EVT because it is built on the assumption that it is to operate in the ATTENDED (MAIL) mode. It is still written out in either case with one small modification for the different mailer types. If you decide to edit the config files outside of ESC you need to be cautious. The configs are white space sensitive concerning how ESC sees them. Pay close attention to how ESC has created the files. Some lines must remain where they are. The EchoArea and Squish Area lists must remain in a contiguous order for ESC to effectively edit them. If at all possible, you should let ESC edit the configs from the menu mode. ESC's PERSONAL NODELIST: ESC needs to know if there have been any changes effecting the NODELIST that it has built. Under most circumstances ESC will detect them on its own. However, if you have another reason to have ESC rewrite and recompile the NODELIST, you may force it to do so with the <J> toggle from the <Nodelist> menu option. Flip it from NODELIST.001 to NO and then back again, and an internal signal is generated telling ESC that it is necessary to rewrite and recompile its NODELIST. After telling ESC to <Write> the pertinent files, it will then seek your permission to recompile NODELIST.001. Editing the MAIL.BAT is permissible except in one area. DO NOT ADD ANYTHING BELOW THE :sqp LABEL! AREAS reads from this file when adding areas. A foreign entry in this section of the batch file will interfere with the work of ESCUTILS.EXE. Plus, anything added just above the :dos label will be lost. If you're running DESQview and Ansi.com no longer provides the escape code translation, you'll have to exit DESQview and start it back up again. This doesn't happen often but it has. * 3.2 POSSIBLE PROBLEMS Most setup problems stem from modem initialization. ESC gives you four choices when configuring. They are: for the USRobotics HST and HST DUAL STANDARD, a GENERIC, simple straight forward string and the option to enter your own string. Please keep in mind that Binkley wants to see the | rather than ^M. So, beware! Also, X00 version 1.24 works superbly with the HST and the D S. It seems to have a problem with some of the 2400 bps modems. BNU is a good choice for 2400 bps or below. -=* Binkley starts and gives some error code. The NODELIST is missing, grundged, improperly processed or not in the specified path. The file BINKLEY.LNG is not in the same directory as BINKLEY.CFG or it hasn't been processed properly. Directories are incorrect in the BINKLEY.CFG. The NODELIST is missing or wasn't compiled properly (if at all). -=* Binkley reports that it is dialing out but nothing is really happening. Try removing the semicolon (;) from in front of the "NoCollide" verb in the BINKLEY.CFG. This disables a feature but is necessary for the success of some modems (i.e. Smart One). -=* Binkley reports that "Remote didn't respond" immediately after it initializes. Try removing the semicolon (;) from in front of the SameRing verb in the BINKLEY.CFG. If all else fails, look to your initialization string. Here is where many people experience problems. -=* You have changed the name of your system or that of your BOSSNODE but Binkley shows the old name when you poll out. You MUST run QNODE (with QIDX) on the NODELIST.001 every time you make a change to the "SYSTEM", "BOSSNODE" or "NODELIST" fields. REMEMBER, Binkley recognizes the | (not the :), as a carriage return. Many modem initialization strings use the ^M convention. Binkley should do the translation when it sends the string to your modem. You may have to experiment with the initialization string and/or modem settings via dip switches or software control (NRAM). The best advice is to read the Binkley manuals as well as all the documentation which comes with your software, especially your modem manual. As simple as it sounds, one problem which seems to occur is that after making changes to the configs, users do not write out the files. After making edits through ESC, be certain to write out the altered file(s), from the Pick List. When in doubt, TAG ALL. Two files are skipped over if ESC detects that they exist when it begins writing files. They are the COMPRESS.CFG and BINKLEY.LNG. The only way to get ESC to rewrite these two is to delete or move them from the home directory. Also, most files are read from and then recreated with some edits. If you want a from scratch file, you should delete it and have ESC rewrite it. Some report strange addresses after setting up. It seems the biggest problem comes from not knowing whether a 3d (privatenet) or 4d address is appropriate. To compound the confusion, some utilities show a 4d address even though the system is configured as 3d. Msged will show the 4d address regardless of point types. Never the less, it is important to understand which type you are. If your boss assigns you a number different from his own, then you are 3d. Here's an example below; 1:157/534 BOSS ADDRESS 1:3534/109 3d POINT ADDRESS 1:157/534.109 4d POINT ADDRESS If the number which you have been assigned, after the colon is different than the BOSS address as above, then you have a 3d address. If it is the same, then you have a 4d address. Also, 3d addresses will not have a period delimiting them. * 4.1 ACKNOWLEDGEMENTS Todd Smith of 157/100@fidonet aka 157/533: Many of the features in ESC are a result of his suggestions. He stands unique as the primary and original beta tester as well as the one who promoted the insurgence of many FIDONET members in this locale. This prompted the beginning efforts on such a project as ESC. Jim Ball of 157/534.11 provided great assistance and scrutiny. Many features were conceived and implemented because of his thoughtful recommendation and painstaking bug detection. Ed Marsh of 157/534.12 as beta tester and documentation editor, who also quite thoroughly tested the programs from a perspective of one newly entered into telecommunications. Kevin Benton of 157/516@fidonet answered questions and provided snippets of code. This is my first programming effort for IBM class machines and his help was essential. Don Benson of 157/603@fidonet who enjoyed making me angry by rolling his forehead back and forth over the keyboard to see what kind of errors he could get the programs to generate. Don is also responsible for the "Color2" scheme which most seem to prefer. He made other recommendations but five lines is all he's getting. Glen Gilbert 1:157/534@fidonet is the author. Now that you have this package, please send a netmail message his way containing comments, bug reports and suggestions. If you chose to use the NODELIST creation feature, then his name and address are included there, as well as that of Todd Smith (support system). In other words, just type in either name while in Msged and the correct fidonet address should pop up. Both will be watching the POINTS echo for any interest in ESC. The intention is to support, and develop it further, respective to the amount of interest. SQUISH - is the creation of Scott Dudley. BINKLEY - is the creation of Vince Perriello and Bob Hartman. MSGED - is the creation of Jim Nutt and John Dennis is the - developer of the Squish-compatible version. QNODE - is the creation of James West BONK - is the creation of Tom Kashuba and Ulf Nilsson YABOM - is the creation of Berin Lautenbach WIMM - is the creation of Gerard van Essen * 4.2 DISCLAIMER ┌────────────────────────────────────────────────┐ │ There is no warrantee and the author takes │ │ zero responsibility for whatever happens │ │ when using this software. Accepting or │ │ running any of the files included with this │ │ package acknowledges your acceptance of │ │ these terms. If in doubt, simply delete them. │ └────────────────────────────────────────────────┘ * 4.3 BUG and PROBLEM REPORTS Please send your questions, problems and bug reports about Esc to -- Glen Gilbert of 1:157/534@fidonet It is very important that you give the Esc version number! Send the ESC.CFG and other pertinent configuration or batch files if possible. "The quality of the help you receive, is directly proportional to the information you provide." * 4.4 UPGRADING When upgrading from a previous ESC setup BACK UP first! As of version 1.46, ESC will save your message area declarations in two files. They are M_AREA.DAT and S_AREA.DAT. ESC will find and read the content of these files, placing the entries found in them, into the newly created MSGED.CFG and SQUISH.CFG. The MSGED.CFG is not relevant to GOLDED users. Caution should be exercised when reinstalling. Edits to the MAIL.BAT (other than squish maintenance functions) will be lost. * 4.5 CUSTOMIZING You may have already figured out that you can fully customize nearly every function of the ESC shell. The place to change the order of operation or options is in the MAIL.BAT. If you want to keep the ESC batch file menu system and find the colors a bit too much to deal with. You may change the ansi escape codes. A file was distributed with the earlier ESC releases called KEYCHART.TXT. This file had several screens explaining and listing Ansi codes and your keyboard scan codes. It would be worth your while to look this file over if can have it. Most Dos manuals have much of the information found in this KEYCHART.TXT. * 5.1 GLOSSARY NOTE: This listing of terms is presented in a LOGICAL rather than ALPHABETICAL order, so that new terms can be understood from the preceding ones. FIDONET - A conglomeration of people and their computers in agreement to pass electronically produced messages and files to one another. Tom Jennings of Fido Software is accredited as the originator of fidonet. NETWORK - The system of computers connected to each other through telephone lines. In this case, computers owned and/or operated by FIDONET amateur enthusiasts. FTS ... Fido Technical Standard - rules developed and agreed upon by the fathers and experts of this amateur electronic mail network. (FIDONET) BOSSNODE ... HOST SYSTEM - the system from which you receive your mail. BOSS ... THE HOST - The sysOp (system operator) of the system mentioned above. FEED ... The system associated with supplying echomail or files to another. Also referred to as a HOST, BOSSNODE or BOSS system. MAILER - Terminal software which uses your modem and operates under the Fido Technical Standards for handshaking and protocol concerning the passing of electronic mail bundles. MAIL PROCESSOR - The software which handles mail bundles and individual messages. Examining and TOSSing each message and placing them into the proper directory and/or file. Also, in the case of SQUISH, scanning through these directories and/or files for newly created messages, collecting and placing any found into packets. This operation is referred to as PACKing. These PACKets are optionally collected into larger bundles, and named appropriately with a hexadecimal filename which is understood by the MAILER. "Optionally" means that it is possible for individual packets to be passed without bundling. MESSAGE EDITOR/READER - Software designed to create and read messages of the FTS format. MATRIX - The network of systems coordinated to pass electronic mail. NODELIST - A file published from 1:1/0 out of St. Louis Missouri which is an FTS directory containing all necessary information needed for an FTS mailer to pass mail to another FTS compatible system. NODEDIFF - A weekly publication from the same source listed above which adds, subtracts or corrects entries of the NODELIST. NODELIST PROCESSOR - Software which processes the raw files of the NODELIST and/or NODEDIFF into usable and configurable format used by various FTS software. Particularly the MAILER. ZONE - A geographical area (continent) used to determine the origin or destination of electronic mail REGION - A subordinate (smaller) area within a ZONE. NET - A network of FTS compatible systems within a REGION. NODE - A particular system within a NET. POINT - A subsystem which is served from a NODE. POINTs are considered dead end mailers. Meaning, echomail is received from a single source (the BOSSNODE normally). All ECHOMAIL generated on the POINT system is to be passed only to the BOSSNODE for processing. In other words, ECHOMAIL is not to be passed to another system other than the one from which echo mail is being received. Otherwise, the POINT must become a NODE and have their address in the NODELIST. NETMAIL may be ROUTED either through the BOSSNODE or directly to the system addressed. HUB - A system which collects electronic mail and distributes it to other systems. Usually receiving large volumes from a network or regional collection site and then distributing it to the NODES and optionally POINTS associated with it. VERB or TOKEN - Configuration files contain key words which act as signals to the program they exist for. These keywords are often referred to by either of these terms. NETMAIL - is the term used for non echoing electronic mail which is not posted indiscreetly. It can take on one of two forms: Direct or Routed. Both terms define the action taken in order to transfer these types of messages. DIRECT goes from one system directly to another without stopping on any other system. It would be equivalent to personally handing a sealed letter to the person it is addressed to. ROUTED is the equivalent of sending that same letter via one or more trusted friends. Under most circumstances, this semi private mail can be read by the operators of the system through which your mail is passing. ECHOMAIL - is the term used for messages which may have a particular recipient in mind but are posted very publicly. Sending echomail can be compared to putting an add in the classifieds. Where everyone gets to read your message which gets moved along through many systems and is displayed to anyone who has access to that system. End of ESC documentation.